perf: build file-name array without intermediate list - #421
Conversation
|
Warning Review limit reached
Next review available in: 52 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Problem
PR #400 and duplicate #407 identify one valid allocation boundary, but both branches predate current protected
masterand conflict with later security/accessibility work. Their unmeasured “50% faster” and inherited test claims are not reused.Current-base reconstruction
Exact base:
master@187449c87e44d0e72f3c3016499f506f9fe41ba6.map { it.name }.toTypedArray()with one directly initializedArray(files.size);This is the single successor to #400 and closed duplicate #407.
Acceptance boundary
Merge only after unchanged-head CI, coverage, security, SAST, current-head review, zero valid unresolved findings, and live repository policy succeed.